Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd054c5e156cb0d042f46b480250c2f358034593758e4ea71e82f6d70c270204

Tx prefix hash: 719b8e78c0cc12ad33c59bc2cdc100e2b113ab79e95aa6b78d8532b7868285d2
Tx public key: a6d6a8cc8c36058e6779539f81cfb3816e4bbc62ded5d6845f8de3ae65525973
Timestamp: 1726388513 Timestamp [UCT]: 2024-09-15 08:21:53 Age [y:d:h:m:s]: 00:204:11:00:47
Block: 1110525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145936 RingCT/type: yes/0
Extra: 01a6d6a8cc8c36058e6779539f81cfb3816e4bbc62ded5d6845f8de3ae65525973021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be81ef833fa0da9ae2766ca91fde4cc4bcd097ff0bd372390a615f423e9a498d 0.600000000000 1589160 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": 1110535, "vin": [ { "gen": { "height": 1110525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be81ef833fa0da9ae2766ca91fde4cc4bcd097ff0bd372390a615f423e9a498d" } } ], "extra": [ 1, 166, 214, 168, 204, 140, 54, 5, 142, 103, 121, 83, 159, 129, 207, 179, 129, 110, 75, 188, 98, 222, 213, 214, 132, 95, 141, 227, 174, 101, 82, 89, 115, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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