Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ce548dfb64bcdf5b6be26b00c13dbc68f6d809cce21aab26014e9dd59dea264

Tx prefix hash: 2e7f935015429cd2d43d78f5fd87461f4a4bf7ff6428ffaf4e8877d7c3856c28
Tx public key: 74fdd5ffa8d41e0593fcf70a47a85cb265f7d85e7907b0926a55a7acf81b5264
Timestamp: 1710101553 Timestamp [UCT]: 2024-03-10 20:12:33 Age [y:d:h:m:s]: 01:006:15:02:03
Block: 975507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265729 RingCT/type: yes/0
Extra: 0174fdd5ffa8d41e0593fcf70a47a85cb265f7d85e7907b0926a55a7acf81b52640211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6558e8657c8c5fe4ce31b24d5356f522ca32da0e50197b304fddbd9452a1853 0.600000000000 1435480 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": 975517, "vin": [ { "gen": { "height": 975507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6558e8657c8c5fe4ce31b24d5356f522ca32da0e50197b304fddbd9452a1853" } } ], "extra": [ 1, 116, 253, 213, 255, 168, 212, 30, 5, 147, 252, 247, 10, 71, 168, 92, 178, 101, 247, 216, 94, 121, 7, 176, 146, 106, 85, 167, 172, 248, 27, 82, 100, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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