Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5b54bdbe38f8eacbbc08880d0e30e5d98d326ee3fe80320e2c217d6ab57cd8

Tx prefix hash: b115d2dc9612bf6b609d0263961926ee96dc358747d35cc42506f45b66529e48
Tx public key: 452ac92c9c6ba29ea17703238b762a62f6bf4706e708824093935808104cd7e9
Timestamp: 1612794982 Timestamp [UCT]: 2021-02-08 14:36:22 Age [y:d:h:m:s]: 04:265:12:15:53
Block: 194574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207067 RingCT/type: yes/0
Extra: 01452ac92c9c6ba29ea17703238b762a62f6bf4706e708824093935808104cd7e9021100000162c6b81c9d000000000000000000

1 output(s) for total of 139.090092941000 dcy

stealth address amount amount idx
00: bcc1de6b0a9e3256cbcffe348020fd1e05dcfb157a11b811702b4cc54581d7ea 139.090092941000 395174 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": 194584, "vin": [ { "gen": { "height": 194574 } } ], "vout": [ { "amount": 139090092941, "target": { "key": "bcc1de6b0a9e3256cbcffe348020fd1e05dcfb157a11b811702b4cc54581d7ea" } } ], "extra": [ 1, 69, 42, 201, 44, 156, 107, 162, 158, 161, 119, 3, 35, 139, 118, 42, 98, 246, 191, 71, 6, 231, 8, 130, 64, 147, 147, 88, 8, 16, 76, 215, 233, 2, 17, 0, 0, 1, 98, 198, 184, 28, 157, 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