Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 623e1bf56868335159ce6241ee604f13697d719e8c3ab00a2b86ee251719c036

Tx prefix hash: 95e5c74521d11cfd320154ad21e1fbaa21132c05f1ad945c9eaaba736aeafe48
Tx public key: a35be32da132f71a6a113a92d4d1ea4fee71758a45b17e5c8f71cc3e43f7b1f8
Timestamp: 1729272608 Timestamp [UCT]: 2024-10-18 17:30:08 Age [y:d:h:m:s]: 00:019:22:56:28
Block: 1134432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14207 RingCT/type: yes/0
Extra: 01a35be32da132f71a6a113a92d4d1ea4fee71758a45b17e5c8f71cc3e43f7b1f80211000000033cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fff486d8226c70831abb35a50cc0be00df9faac55b09324d0cd2a32b779596a 0.600000000000 1617735 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": 1134442, "vin": [ { "gen": { "height": 1134432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fff486d8226c70831abb35a50cc0be00df9faac55b09324d0cd2a32b779596a" } } ], "extra": [ 1, 163, 91, 227, 45, 161, 50, 247, 26, 106, 17, 58, 146, 212, 209, 234, 79, 238, 113, 117, 138, 69, 177, 126, 92, 143, 113, 204, 62, 67, 247, 177, 248, 2, 17, 0, 0, 0, 3, 60, 208, 252, 6, 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