Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0994fb8d10e49ef08f1539ed7e0eca343fb57f274d9182750585d1d3b50b3a

Tx prefix hash: 58d171565f1cfa387b3df657c5b0c42f5a29bd09aad96ad71f7d009557117e2b
Tx public key: 6fbb286eaa471f1e45f2661f1c748d151f4e040d4ff2814385181a215864e881
Timestamp: 1700402595 Timestamp [UCT]: 2023-11-19 14:03:15 Age [y:d:h:m:s]: 01:133:07:57:31
Block: 895087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356464 RingCT/type: yes/0
Extra: 016fbb286eaa471f1e45f2661f1c748d151f4e040d4ff2814385181a215864e88102110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.664056743000 dcy

stealth address amount amount idx
00: 4771892fcb0e6664b28f4b98d28667310c44e57b2c6ca44628a5a692a2182bf7 0.664056743000 1351308 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": 895097, "vin": [ { "gen": { "height": 895087 } } ], "vout": [ { "amount": 664056743, "target": { "key": "4771892fcb0e6664b28f4b98d28667310c44e57b2c6ca44628a5a692a2182bf7" } } ], "extra": [ 1, 111, 187, 40, 110, 170, 71, 31, 30, 69, 242, 102, 31, 28, 116, 141, 21, 31, 78, 4, 13, 79, 242, 129, 67, 133, 24, 26, 33, 88, 100, 232, 129, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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