Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d1eef95a2b8768e7f33111c16dc804e5c42dcaae44fddb0022848f7a3b0cef

Tx prefix hash: 8c1f8c892237a6c02f23a80fcde80e4def330c762fc5f7d7740fd6d907f80f73
Tx public key: 43a62047427a32bc618ad1ee66519ce5daa580d4d10e89755a312f7cdeb713d7
Timestamp: 1755746148 Timestamp [UCT]: 2025-08-21 03:15:48 Age [y:d:h:m:s]: 00:097:13:07:57
Block: 1351027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69633 RingCT/type: yes/0
Extra: 0143a62047427a32bc618ad1ee66519ce5daa580d4d10e89755a312f7cdeb713d7021100000006ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47f6a95a1896dbac0fe67277f87fde35fc7286fe2f88224acd87259aca0aba06 0.600000000000 1838974 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": 1351037, "vin": [ { "gen": { "height": 1351027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47f6a95a1896dbac0fe67277f87fde35fc7286fe2f88224acd87259aca0aba06" } } ], "extra": [ 1, 67, 166, 32, 71, 66, 122, 50, 188, 97, 138, 209, 238, 102, 81, 156, 229, 218, 165, 128, 212, 209, 14, 137, 117, 90, 49, 47, 124, 222, 183, 19, 215, 2, 17, 0, 0, 0, 6, 173, 121, 72, 208, 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