Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb91bb872a5976b60b4ef070b7c5966b3cea6052fefc6808edb64272f2965e6

Tx prefix hash: e3bc8a92316c020d653a9f176d4d091afb3c587be6b189b7279927ddc1877843
Tx public key: e4754e2538f8580a463acd36447cd28c080fbbef42cde40dc8aa0e048c2e4a5d
Timestamp: 1703113602 Timestamp [UCT]: 2023-12-20 23:06:42 Age [y:d:h:m:s]: 01:181:21:10:04
Block: 917585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390996 RingCT/type: yes/0
Extra: 01e4754e2538f8580a463acd36447cd28c080fbbef42cde40dc8aa0e048c2e4a5d021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f3315726f2e5f4d2d0c8d9519e0ca255d464c20bc09fef49186d5f1343cba3 0.600000000000 1375167 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": 917595, "vin": [ { "gen": { "height": 917585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f3315726f2e5f4d2d0c8d9519e0ca255d464c20bc09fef49186d5f1343cba3" } } ], "extra": [ 1, 228, 117, 78, 37, 56, 248, 88, 10, 70, 58, 205, 54, 68, 124, 210, 140, 8, 15, 187, 239, 66, 205, 228, 13, 200, 170, 14, 4, 140, 46, 74, 93, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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