Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff86c6860f31b82bb951444d24f055920d905c80a218d3044a44e0eacc85dd8f

Tx prefix hash: b27a6e5596dc651c850a8388fcccfc3c3268bf6017f40cde91f200073102c366
Tx public key: 9d7e4bc0b83e62e5ed75a2bf0ca831e49e14d7838664134eb79efc4bd18c18fd
Timestamp: 1731317587 Timestamp [UCT]: 2024-11-11 09:33:07 Age [y:d:h:m:s]: 00:147:23:08:25
Block: 1151287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105569 RingCT/type: yes/0
Extra: 019d7e4bc0b83e62e5ed75a2bf0ca831e49e14d7838664134eb79efc4bd18c18fd021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ee31e77e25b32a9ccb7f9e3b64a0947bb4962a09387ee5e56cf58a9e7bc4a9d 0.600000000000 1636792 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": 1151297, "vin": [ { "gen": { "height": 1151287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ee31e77e25b32a9ccb7f9e3b64a0947bb4962a09387ee5e56cf58a9e7bc4a9d" } } ], "extra": [ 1, 157, 126, 75, 192, 184, 62, 98, 229, 237, 117, 162, 191, 12, 168, 49, 228, 158, 20, 215, 131, 134, 100, 19, 78, 183, 158, 252, 75, 209, 140, 24, 253, 2, 17, 0, 0, 0, 5, 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