Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3d65b475c7c85d1888a5545cd466fc048f7a5f7588cc163af8c2111157c49a4

Tx prefix hash: 2770957a371daca40f6250c27c403b58a2fe2af361e8853774e66e756051d787
Tx public key: 8abb65d535c2be4a951ee4b7b0c22dafdb619c0c8d175ed93494af41335c01b6
Timestamp: 1732035219 Timestamp [UCT]: 2024-11-19 16:53:39 Age [y:d:h:m:s]: 00:166:00:39:53
Block: 1157247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118486 RingCT/type: yes/0
Extra: 018abb65d535c2be4a951ee4b7b0c22dafdb619c0c8d175ed93494af41335c01b6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44c99277070ad46d9ca8af907033eae61297c143b7a77f8c0d84410c7923db1b 0.600000000000 1642870 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": 1157257, "vin": [ { "gen": { "height": 1157247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44c99277070ad46d9ca8af907033eae61297c143b7a77f8c0d84410c7923db1b" } } ], "extra": [ 1, 138, 187, 101, 213, 53, 194, 190, 74, 149, 30, 228, 183, 176, 194, 45, 175, 219, 97, 156, 12, 141, 23, 94, 217, 52, 148, 175, 65, 51, 92, 1, 182, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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