Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 181c81870e229610089a0892f7802a0bcfcd89b85724e8b04ea24b5d9451b837

Tx prefix hash: 71ee33db51261515781c25313a9156609b177d229d2d1c17e4938b017f12c8cf
Tx public key: b2ff5cf9418bee914b335e4379c5a8a93841bd525d88c55e74da192b7d611f4e
Timestamp: 1729438711 Timestamp [UCT]: 2024-10-20 15:38:31 Age [y:d:h:m:s]: 00:155:19:36:05
Block: 1135822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111114 RingCT/type: yes/0
Extra: 01b2ff5cf9418bee914b335e4379c5a8a93841bd525d88c55e74da192b7d611f4e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a800075632d02075e9181969111de018b9c2ea05743078d66e5d4e18e06033a 0.600000000000 1619161 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": 1135832, "vin": [ { "gen": { "height": 1135822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a800075632d02075e9181969111de018b9c2ea05743078d66e5d4e18e06033a" } } ], "extra": [ 1, 178, 255, 92, 249, 65, 139, 238, 145, 75, 51, 94, 67, 121, 197, 168, 169, 56, 65, 189, 82, 93, 136, 197, 94, 116, 218, 25, 43, 125, 97, 31, 78, 2, 17, 0, 0, 0, 3, 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