Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ddc19a9108bee0ea9acfea1234fdae5851897f85762cdbbd66ce0d6fc7063f6

Tx prefix hash: 51d4df7cbc56083f060db51f5008ab59c968165d4410f9c675402a1415def5d2
Tx public key: 4df6ca3a437119acefae1ad1f8b1a31ad56394a8e1fd3754a2f4d222cff478a0
Timestamp: 1577667822 Timestamp [UCT]: 2019-12-30 01:03:42 Age [y:d:h:m:s]: 04:361:17:02:38
Block: 34674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147658 RingCT/type: yes/0
Extra: 014df6ca3a437119acefae1ad1f8b1a31ad56394a8e1fd3754a2f4d222cff478a0021100000036e39b962a000000000000000000

1 output(s) for total of 471.098259348000 dcy

stealth address amount amount idx
00: 116a2cee3907340726b7d0f7c68ea9866e62f47b26bd9fde8c76fd35c3b98c1f 471.098259348000 58384 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": 34684, "vin": [ { "gen": { "height": 34674 } } ], "vout": [ { "amount": 471098259348, "target": { "key": "116a2cee3907340726b7d0f7c68ea9866e62f47b26bd9fde8c76fd35c3b98c1f" } } ], "extra": [ 1, 77, 246, 202, 58, 67, 113, 25, 172, 239, 174, 26, 209, 248, 177, 163, 26, 213, 99, 148, 168, 225, 253, 55, 84, 162, 244, 210, 34, 207, 244, 120, 160, 2, 17, 0, 0, 0, 54, 227, 155, 150, 42, 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