Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07516045e73bc108b6179372457804083c84c2f4ccec9abc75bf6a314d49f08f

Tx prefix hash: 8e25e9b61b2d1e9aa47bef89b9833e75f46f24a1a409103d4d845d603d11b4e6
Tx public key: 81996011eb4d18175225c497a2f1042b2d39a34d77291996e83007f2ac575ec5
Timestamp: 1641068228 Timestamp [UCT]: 2022-01-01 20:17:08 Age [y:d:h:m:s]: 03:072:15:54:27
Block: 408386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 830734 RingCT/type: yes/0
Extra: 0181996011eb4d18175225c497a2f1042b2d39a34d77291996e83007f2ac575ec5021100000001e2bb00ee000000000000000000

1 output(s) for total of 27.217484987000 dcy

stealth address amount amount idx
00: 4d2372a5e04435763ea6f474421e9f101414188d9d4341c4c9e3e5275440d3c3 27.217484987000 810405 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": 408396, "vin": [ { "gen": { "height": 408386 } } ], "vout": [ { "amount": 27217484987, "target": { "key": "4d2372a5e04435763ea6f474421e9f101414188d9d4341c4c9e3e5275440d3c3" } } ], "extra": [ 1, 129, 153, 96, 17, 235, 77, 24, 23, 82, 37, 196, 151, 162, 241, 4, 43, 45, 57, 163, 77, 119, 41, 25, 150, 232, 48, 7, 242, 172, 87, 94, 197, 2, 17, 0, 0, 0, 1, 226, 187, 0, 238, 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