Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d4d8a4ca6018712b7379295fa174c4dcd9cdbfbdbe9563abe4b5ab318d03c64

Tx prefix hash: 23da3f4d8ca22f1ff6e08c328b8645818ce2b3829b7774e497a9848279d338c7
Tx public key: f66c78955fa85de39ea4a843c3a091888c423d7ea5fbca4ea39a18bcf8d820ab
Timestamp: 1577010366 Timestamp [UCT]: 2019-12-22 10:26:06 Age [y:d:h:m:s]: 05:118:21:26:36
Block: 29596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1234407 RingCT/type: yes/0
Extra: 01f66c78955fa85de39ea4a843c3a091888c423d7ea5fbca4ea39a18bcf8d820ab0211000000064943cd9f000000000000000000

1 output(s) for total of 489.707808497000 dcy

stealth address amount amount idx
00: cf6dce9670319d31cd39ead781dc2ce0f86e38df5dd52812ca163a0a373a6fca 489.707808497000 48692 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": 29606, "vin": [ { "gen": { "height": 29596 } } ], "vout": [ { "amount": 489707808497, "target": { "key": "cf6dce9670319d31cd39ead781dc2ce0f86e38df5dd52812ca163a0a373a6fca" } } ], "extra": [ 1, 246, 108, 120, 149, 95, 168, 93, 227, 158, 164, 168, 67, 195, 160, 145, 136, 140, 66, 61, 126, 165, 251, 202, 78, 163, 154, 24, 188, 248, 216, 32, 171, 2, 17, 0, 0, 0, 6, 73, 67, 205, 159, 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