Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25912991246c1c434d8de51dbdd7d982321314e9d9c5098e4b10a50dc01ac718

Tx prefix hash: b1b8204d77c84ff26375a6f5d832597fe0832a937f957eae2b551ada677dbc01
Tx public key: 035e6ebd7686f77b4b2e7f91dba6f13c6f02a526c0462b4a5f445bd3f9498939
Timestamp: 1715232707 Timestamp [UCT]: 2024-05-09 05:31:47 Age [y:d:h:m:s]: 01:021:01:43:09
Block: 1018032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276006 RingCT/type: yes/0
Extra: 01035e6ebd7686f77b4b2e7f91dba6f13c6f02a526c0462b4a5f445bd3f949893902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eca0f1c89741f0777eb3c6020d6ec0209134cfaf8db8df2faeeec2d4fd7258ea 0.600000000000 1481817 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": 1018042, "vin": [ { "gen": { "height": 1018032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eca0f1c89741f0777eb3c6020d6ec0209134cfaf8db8df2faeeec2d4fd7258ea" } } ], "extra": [ 1, 3, 94, 110, 189, 118, 134, 247, 123, 75, 46, 127, 145, 219, 166, 241, 60, 111, 2, 165, 38, 192, 70, 43, 74, 95, 68, 91, 211, 249, 73, 137, 57, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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