Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3dbc0a83c77d945b0f47146fd8ee03b68814d9b87c8ddd9e949c19023251357

Tx prefix hash: 4a1dd124e89cef5dd4c9d59dcfcffb6a9171a16b1599d72b3919789c3b8b42e5
Tx public key: a2f573c708e19643be02185d56e55a0e6f919a5cbf55f2e7af811d3797e4bbf6
Timestamp: 1734792888 Timestamp [UCT]: 2024-12-21 14:54:48 Age [y:d:h:m:s]: 00:313:18:02:59
Block: 1180107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221719 RingCT/type: yes/0
Extra: 01a2f573c708e19643be02185d56e55a0e6f919a5cbf55f2e7af811d3797e4bbf60211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 274643f63cbf53e9cb7fb0098593fe2898d9e458a3d8e3901b0c7a35ab667a53 0.600000000000 1666512 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": 1180117, "vin": [ { "gen": { "height": 1180107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "274643f63cbf53e9cb7fb0098593fe2898d9e458a3d8e3901b0c7a35ab667a53" } } ], "extra": [ 1, 162, 245, 115, 199, 8, 225, 150, 67, 190, 2, 24, 93, 86, 229, 90, 14, 111, 145, 154, 92, 191, 85, 242, 231, 175, 129, 29, 55, 151, 228, 187, 246, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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