Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1788e4fa729623d979103540d378049da302ca7d1695edda610d121bddc1ef2

Tx prefix hash: 0c56107b8cb4ed7b5be1e8d314bda91898f3536b0f3bb81ac330d614e75d3a3a
Tx public key: ec3df6d5d3d268f2db6509b6344ea23640edd3352a291f36d58cf8c169cb1770
Timestamp: 1722385004 Timestamp [UCT]: 2024-07-31 00:16:44 Age [y:d:h:m:s]: 00:268:19:02:56
Block: 1077330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192026 RingCT/type: yes/0
Extra: 01ec3df6d5d3d268f2db6509b6344ea23640edd3352a291f36d58cf8c169cb177002110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e987233b5242af6200106e075fa112be72c11eaaf90b636d1a8e9bbee09ab33 0.600000000000 1549877 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": 1077340, "vin": [ { "gen": { "height": 1077330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e987233b5242af6200106e075fa112be72c11eaaf90b636d1a8e9bbee09ab33" } } ], "extra": [ 1, 236, 61, 246, 213, 211, 210, 104, 242, 219, 101, 9, 182, 52, 78, 162, 54, 64, 237, 211, 53, 42, 41, 31, 54, 213, 140, 248, 193, 105, 203, 23, 112, 2, 17, 0, 0, 0, 9, 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