Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2a9cbfd2c46378999651e0efa79eb047d39492c2e41957f8fbe1b68b67215bb

Tx prefix hash: e1921debeb31d3bd6c4309fc2e30bf3f362b3e90ed9957ad76df75a5d32d510a
Tx public key: 324ed7319364c65f6460a38a1acbc74bb0d912fae73d8b70f3681566463dac5e
Timestamp: 1730638456 Timestamp [UCT]: 2024-11-03 12:54:16 Age [y:d:h:m:s]: 00:003:19:56:11
Block: 1145672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2745 RingCT/type: yes/0
Extra: 01324ed7319364c65f6460a38a1acbc74bb0d912fae73d8b70f3681566463dac5e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bd07fed3b5edd6e2b7335a5cf8f594ee3e3352c9fd04a9c1e1d8176b0c41eeb 0.600000000000 1630161 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": 1145682, "vin": [ { "gen": { "height": 1145672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bd07fed3b5edd6e2b7335a5cf8f594ee3e3352c9fd04a9c1e1d8176b0c41eeb" } } ], "extra": [ 1, 50, 78, 215, 49, 147, 100, 198, 95, 100, 96, 163, 138, 26, 203, 199, 75, 176, 217, 18, 250, 231, 61, 139, 112, 243, 104, 21, 102, 70, 61, 172, 94, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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