Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 651d6b7321e49f632ac0c57c6751fbaea569459539a0d3dedf6c6684bd105fa0

Tx prefix hash: a196d2029f487dce390dc4c4d7b092bd13be3cba8b2372971207b088f035389d
Tx public key: 352a5247bcd7f82ec939b4cd4a23fd3b49b48de54963156be483b3658c3218de
Timestamp: 1639414850 Timestamp [UCT]: 2021-12-13 17:00:50 Age [y:d:h:m:s]: 03:324:22:14:01
Block: 394747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1008679 RingCT/type: yes/0
Extra: 01352a5247bcd7f82ec939b4cd4a23fd3b49b48de54963156be483b3658c3218de021100000003eaa12622000000000000000000

1 output(s) for total of 30.202276615000 dcy

stealth address amount amount idx
00: 9a6ec0d57b511b876f2c0bf3a2277d6e9a67715a730eaafb5698963504c708ec 30.202276615000 792440 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": 394757, "vin": [ { "gen": { "height": 394747 } } ], "vout": [ { "amount": 30202276615, "target": { "key": "9a6ec0d57b511b876f2c0bf3a2277d6e9a67715a730eaafb5698963504c708ec" } } ], "extra": [ 1, 53, 42, 82, 71, 188, 215, 248, 46, 201, 57, 180, 205, 74, 35, 253, 59, 73, 180, 141, 229, 73, 99, 21, 107, 228, 131, 179, 101, 140, 50, 24, 222, 2, 17, 0, 0, 0, 3, 234, 161, 38, 34, 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