Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbac216113916a45dec96d6c67a6d02a7bf7598efd1297acbf386da4e01605d2

Tx prefix hash: f66f0b86e766dd0499ae2a77739dd80ae7e8722c1f5cedae162cba5a33c87f2d
Tx public key: 8f58c4d4251c718a4d0c171ed77d96c22688486094e08077b09204edda169b31
Timestamp: 1723559179 Timestamp [UCT]: 2024-08-13 14:26:19 Age [y:d:h:m:s]: 00:303:21:15:16
Block: 1087066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217047 RingCT/type: yes/0
Extra: 018f58c4d4251c718a4d0c171ed77d96c22688486094e08077b09204edda169b3102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26b2acd3ecbee6f24f9690ecd59dde4adb95d1a6c55d3e0d52d05d9c15720128 0.600000000000 1561671 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": 1087076, "vin": [ { "gen": { "height": 1087066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26b2acd3ecbee6f24f9690ecd59dde4adb95d1a6c55d3e0d52d05d9c15720128" } } ], "extra": [ 1, 143, 88, 196, 212, 37, 28, 113, 138, 77, 12, 23, 30, 215, 125, 150, 194, 38, 136, 72, 96, 148, 224, 128, 119, 176, 146, 4, 237, 218, 22, 155, 49, 2, 17, 0, 0, 0, 5, 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