Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23b545d19d9803f8e626121efa57faa7182ab4ed5df199ac15f9861fef964421

Tx prefix hash: b94f89526025566658ccb699ab568aade87c1fd82d137508facb2f4760e1f368
Tx public key: fc5a6c9f9ca1a1b036a781ca30f9654c24f8c723a5f6910141ed9408028dd4c6
Timestamp: 1724100692 Timestamp [UCT]: 2024-08-19 20:51:32 Age [y:d:h:m:s]: 00:214:11:31:57
Block: 1091557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153149 RingCT/type: yes/0
Extra: 01fc5a6c9f9ca1a1b036a781ca30f9654c24f8c723a5f6910141ed9408028dd4c602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77b9107e79bada724a357c42d097fbbadd03f2e8570b8eaee533502f3af2b107 0.600000000000 1566190 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": 1091567, "vin": [ { "gen": { "height": 1091557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77b9107e79bada724a357c42d097fbbadd03f2e8570b8eaee533502f3af2b107" } } ], "extra": [ 1, 252, 90, 108, 159, 156, 161, 161, 176, 54, 167, 129, 202, 48, 249, 101, 76, 36, 248, 199, 35, 165, 246, 145, 1, 65, 237, 148, 8, 2, 141, 212, 198, 2, 17, 0, 0, 0, 4, 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