Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71f5477c9b817d99c18acdedf40940de542da1cc0f6c6834a8b224061ee5f89e

Tx prefix hash: 0dfaeeca64f812a4d0f8cec0dd65f9f8059180f8c0c684c1b8f727df9bd71631
Tx public key: cea16f29fb795ce0cf09d202326bfc3b79b238e52dd4d642a17daedbbf236afc
Timestamp: 1720756456 Timestamp [UCT]: 2024-07-12 03:54:16 Age [y:d:h:m:s]: 00:181:00:30:04
Block: 1063838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129512 RingCT/type: yes/0
Extra: 01cea16f29fb795ce0cf09d202326bfc3b79b238e52dd4d642a17daedbbf236afc02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1880a9e0659947115f2f23848a27a587df6f522bf7ddbb88122d15277a00013b 0.600000000000 1534355 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": 1063848, "vin": [ { "gen": { "height": 1063838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1880a9e0659947115f2f23848a27a587df6f522bf7ddbb88122d15277a00013b" } } ], "extra": [ 1, 206, 161, 111, 41, 251, 121, 92, 224, 207, 9, 210, 2, 50, 107, 252, 59, 121, 178, 56, 229, 45, 212, 214, 66, 161, 125, 174, 219, 191, 35, 106, 252, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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