Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5396d356f4a77a94191a7aa846a1a76f67fa08a496b17648f26bbb2fb8eba013

Tx prefix hash: 590e3c68efec3fb9d1cb73afeebd4527b8dc9605ba7d38a92f2bfd316beb52e0
Tx public key: 56d28f8bd6641e11cf67a907fe9f4c5232e97f15c786c72156e4d78e3a436319
Timestamp: 1736991234 Timestamp [UCT]: 2025-01-16 01:33:54 Age [y:d:h:m:s]: 00:156:12:16:18
Block: 1198269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111524 RingCT/type: yes/0
Extra: 0156d28f8bd6641e11cf67a907fe9f4c5232e97f15c786c72156e4d78e3a436319021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cc97443aa48c36347fe216a8598bbbe45028e0923b46ec66468e52db199dfe5 0.600000000000 1684890 of 15

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": 1198279, "vin": [ { "gen": { "height": 1198269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cc97443aa48c36347fe216a8598bbbe45028e0923b46ec66468e52db199dfe5" } } ], "extra": [ 1, 86, 210, 143, 139, 214, 100, 30, 17, 207, 103, 169, 7, 254, 159, 76, 82, 50, 233, 127, 21, 199, 134, 199, 33, 86, 228, 215, 142, 58, 67, 99, 25, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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