Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ffc6723a8a2fb2bf900e4454cf22e71f5b0f0be077d5d2034f2df59f898ab26

Tx prefix hash: 6e47f301ebee0c480edf849d63f40bb621d0955c42ab7e97a1d1443c0555dfbe
Tx public key: e085e246c86f732754f6b6e5242cf64ff1a44d1555134609d4bd28a17e0dc39e
Timestamp: 1716240271 Timestamp [UCT]: 2024-05-20 21:24:31 Age [y:d:h:m:s]: 01:170:22:00:46
Block: 1026392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380745 RingCT/type: yes/0
Extra: 01e085e246c86f732754f6b6e5242cf64ff1a44d1555134609d4bd28a17e0dc39e0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfc7dc672a280fca6fc0ee509520c0d6f65aebf03f38e62ae6928f5d11a648dc 0.600000000000 1493449 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": 1026402, "vin": [ { "gen": { "height": 1026392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfc7dc672a280fca6fc0ee509520c0d6f65aebf03f38e62ae6928f5d11a648dc" } } ], "extra": [ 1, 224, 133, 226, 70, 200, 111, 115, 39, 84, 246, 182, 229, 36, 44, 246, 79, 241, 164, 77, 21, 85, 19, 70, 9, 212, 189, 40, 161, 126, 13, 195, 158, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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