Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6584035b9777e5d032e82b78f8912122f3f931a26c09bb3f5ce9e6dac0e25d10

Tx prefix hash: 9e08221508696170f890f111ab831773522e65786f45d34e076cdcb7bfb9233b
Tx public key: 7f2ffbaab941c1a35048991194955e8601b504be415873d7db8c7e855f2dbe2c
Timestamp: 1727546637 Timestamp [UCT]: 2024-09-28 18:03:57 Age [y:d:h:m:s]: 00:171:17:22:59
Block: 1120130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122542 RingCT/type: yes/0
Extra: 017f2ffbaab941c1a35048991194955e8601b504be415873d7db8c7e855f2dbe2c021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57512db911f2f0939a9704e0e0286f59c993b5a4eb4af38ad8e9c9b798dbc499 0.600000000000 1601935 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": 1120140, "vin": [ { "gen": { "height": 1120130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57512db911f2f0939a9704e0e0286f59c993b5a4eb4af38ad8e9c9b798dbc499" } } ], "extra": [ 1, 127, 47, 251, 170, 185, 65, 193, 163, 80, 72, 153, 17, 148, 149, 94, 134, 1, 181, 4, 190, 65, 88, 115, 215, 219, 140, 126, 133, 95, 45, 190, 44, 2, 17, 0, 0, 0, 7, 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