Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1afe321e1e0dd7891ce46d12b88bfdcffd750e5c67ab21268079f538103c3625

Tx prefix hash: b9098bf643eb822895d10076e84543c11f8735a1667d9af354acbfb630b7cec8
Tx public key: 8f50cfdeaaa958f6ab8c3842ebd33645c3a30255e7ae15b3f38b14131c1eb9c6
Timestamp: 1732663718 Timestamp [UCT]: 2024-11-26 23:28:38 Age [y:d:h:m:s]: 00:136:08:43:19
Block: 1162448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97271 RingCT/type: yes/0
Extra: 018f50cfdeaaa958f6ab8c3842ebd33645c3a30255e7ae15b3f38b14131c1eb9c60211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 410ddc690aa37e4bb374277a115fc721d90121894b96b9fd7e9e6e9e2c6d0927 0.600000000000 1648103 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": 1162458, "vin": [ { "gen": { "height": 1162448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "410ddc690aa37e4bb374277a115fc721d90121894b96b9fd7e9e6e9e2c6d0927" } } ], "extra": [ 1, 143, 80, 207, 222, 170, 169, 88, 246, 171, 140, 56, 66, 235, 211, 54, 69, 195, 163, 2, 85, 231, 174, 21, 179, 243, 139, 20, 19, 28, 30, 185, 198, 2, 17, 0, 0, 0, 2, 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