Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1fcc6330b2f8ebd58c7e6ddabb7be7f497e5f2fae49018d63245d26f527a660

Tx prefix hash: 7f9187894d75a7ab75d9010f14f959dfddcedd87bb6d247edf28f7fe7641a353
Tx public key: edd6a1a650e4338ca9db928fb7ae0b46622a1570ad3161a51cf1e0447debb2f3
Timestamp: 1725157456 Timestamp [UCT]: 2024-09-01 02:24:16 Age [y:d:h:m:s]: 01:060:02:58:07
Block: 1100310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301415 RingCT/type: yes/0
Extra: 01edd6a1a650e4338ca9db928fb7ae0b46622a1570ad3161a51cf1e0447debb2f302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f7bd7f5c9c7d1b544d092b109e5bcada9724a93a35578c4909bb4f7561294ba 0.600000000000 1576285 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": 1100320, "vin": [ { "gen": { "height": 1100310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f7bd7f5c9c7d1b544d092b109e5bcada9724a93a35578c4909bb4f7561294ba" } } ], "extra": [ 1, 237, 214, 161, 166, 80, 228, 51, 140, 169, 219, 146, 143, 183, 174, 11, 70, 98, 42, 21, 112, 173, 49, 97, 165, 28, 241, 224, 68, 125, 235, 178, 243, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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