Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b81734894dc95c1d86ba4bb7429eef68dd8058e575fd4f5353acf4dcfda40b53

Tx prefix hash: 8a889c873f2cfc44858c0f4f315092bb2116cbd69238f7569898855def3db7d7
Tx public key: 231be8e08488d1c0179612f72a85886ad859b3dcf5dcd9b4faf6fb514e39a5f8
Timestamp: 1587533251 Timestamp [UCT]: 2020-04-22 05:27:31 Age [y:d:h:m:s]: 05:195:15:18:29
Block: 94674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1308916 RingCT/type: yes/0
Extra: 01231be8e08488d1c0179612f72a85886ad859b3dcf5dcd9b4faf6fb514e39a5f80211000000058a2ee0d9000000000000000000

1 output(s) for total of 298.061927522000 dcy

stealth address amount amount idx
00: c55cd03826254148bbc139f3e28e469263b0c8a60008434d2bd2b34cf4d73f4e 298.061927522000 168506 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 94684, "vin": [ { "gen": { "height": 94674 } } ], "vout": [ { "amount": 298061927522, "target": { "key": "c55cd03826254148bbc139f3e28e469263b0c8a60008434d2bd2b34cf4d73f4e" } } ], "extra": [ 1, 35, 27, 232, 224, 132, 136, 209, 192, 23, 150, 18, 247, 42, 133, 136, 106, 216, 89, 179, 220, 245, 220, 217, 180, 250, 246, 251, 81, 78, 57, 165, 248, 2, 17, 0, 0, 0, 5, 138, 46, 224, 217, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8