Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eae096caa21565822434d9c5444325f0b35e381f95e2d94e31504a4c14ac8440

Tx prefix hash: 80fb1c95c94af87b9841ad1400df95f25968bc525ece6aefd9f443e9ee11d763
Tx public key: afdfee9ce1c8c3c8fa412ca0e1902f44253a481512d2b1a7fb75d63cbf195963
Timestamp: 1726917795 Timestamp [UCT]: 2024-09-21 11:23:15 Age [y:d:h:m:s]: 01:047:15:47:46
Block: 1114906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292467 RingCT/type: yes/0
Extra: 01afdfee9ce1c8c3c8fa412ca0e1902f44253a481512d2b1a7fb75d63cbf195963021100000002bdafe9cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1efa0029b93ed86150fc56fa1937c638721684d8d4c00c0cf6974553b4e8bf04 0.600000000000 1594849 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": 1114916, "vin": [ { "gen": { "height": 1114906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1efa0029b93ed86150fc56fa1937c638721684d8d4c00c0cf6974553b4e8bf04" } } ], "extra": [ 1, 175, 223, 238, 156, 225, 200, 195, 200, 250, 65, 44, 160, 225, 144, 47, 68, 37, 58, 72, 21, 18, 210, 177, 167, 251, 117, 214, 60, 191, 25, 89, 99, 2, 17, 0, 0, 0, 2, 189, 175, 233, 204, 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