Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 009dc715eb96cb70eb6068262601580760dee381207e80919a283d1fe3b87114

Tx prefix hash: 86c0079d4867de56d8a5419d3a15788f57be6a8de029a3e1cebafbe5916bb466
Tx public key: 76fc45276ea5bbc527067f6b3c2e4659d69d57d20c876fec39a4e4723cd16203
Timestamp: 1701175609 Timestamp [UCT]: 2023-11-28 12:46:49 Age [y:d:h:m:s]: 01:189:21:59:52
Block: 901487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396956 RingCT/type: yes/0
Extra: 0176fc45276ea5bbc527067f6b3c2e4659d69d57d20c876fec39a4e4723cd16203021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.632410869000 dcy

stealth address amount amount idx
00: 04967e70a850a71b6a423cc7365eb43a1515ada48afb407f235cf9222793d7d5 0.632410869000 1358050 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": 901497, "vin": [ { "gen": { "height": 901487 } } ], "vout": [ { "amount": 632410869, "target": { "key": "04967e70a850a71b6a423cc7365eb43a1515ada48afb407f235cf9222793d7d5" } } ], "extra": [ 1, 118, 252, 69, 39, 110, 165, 187, 197, 39, 6, 127, 107, 60, 46, 70, 89, 214, 157, 87, 210, 12, 135, 111, 236, 57, 164, 228, 114, 60, 209, 98, 3, 2, 17, 0, 0, 0, 7, 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