Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74ae20f7f706be6500e2a7e37ef8f8b6843d49f7d57057e834d63ff1273015ef

Tx prefix hash: 7e931758ffa05a5f1629fd6e12473f74d572a376f7704a58a44c7a64348d7f53
Tx public key: ebb51fd4fc81ae21db5709de61f1ed96f5d258fece85c51029ddb10c58ea785e
Timestamp: 1676413735 Timestamp [UCT]: 2023-02-14 22:28:55 Age [y:d:h:m:s]: 02:063:08:05:29
Block: 697095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566865 RingCT/type: yes/0
Extra: 01ebb51fd4fc81ae21db5709de61f1ed96f5d258fece85c51029ddb10c58ea785e0211000000035029cbac000000000000000000

1 output(s) for total of 3.007762000000 dcy

stealth address amount amount idx
00: 449f5b70c25cdbb33b2ac8250124f21bed0f0e2f7ef7725b560d61efc820a73a 3.007762000000 1140186 of 0

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": 697105, "vin": [ { "gen": { "height": 697095 } } ], "vout": [ { "amount": 3007762000, "target": { "key": "449f5b70c25cdbb33b2ac8250124f21bed0f0e2f7ef7725b560d61efc820a73a" } } ], "extra": [ 1, 235, 181, 31, 212, 252, 129, 174, 33, 219, 87, 9, 222, 97, 241, 237, 150, 245, 210, 88, 254, 206, 133, 197, 16, 41, 221, 177, 12, 88, 234, 120, 94, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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