Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7501854455f34d211a985f5d21088929b0e221a37571fad3d7f7d164f7df4c4

Tx prefix hash: 666ac55fc70cc425f3b122837254e7372fb835606619f84734e80dadd943c940
Tx public key: fafb11ed50544f2fc0498aa5bc1fbfa450eace2d87aa31764f90f1f26e9731e3
Timestamp: 1711981026 Timestamp [UCT]: 2024-04-01 14:17:06 Age [y:d:h:m:s]: 00:298:08:38:52
Block: 991043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213548 RingCT/type: yes/0
Extra: 01fafb11ed50544f2fc0498aa5bc1fbfa450eace2d87aa31764f90f1f26e9731e30211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdf6ee32f6077d9fc2df3be36a1fdda94bf40e0ff463b6b71c894a56a85f67e4 0.600000000000 1451375 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": 991053, "vin": [ { "gen": { "height": 991043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdf6ee32f6077d9fc2df3be36a1fdda94bf40e0ff463b6b71c894a56a85f67e4" } } ], "extra": [ 1, 250, 251, 17, 237, 80, 84, 79, 47, 192, 73, 138, 165, 188, 31, 191, 164, 80, 234, 206, 45, 135, 170, 49, 118, 79, 144, 241, 242, 110, 151, 49, 227, 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