Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 504ff0bd0435a55235ddebaf5ccc3f9297a5db71399a9b076d52ad7276a44f2f

Tx prefix hash: 4c3cb25d7d40739c6fb0462a6906a3d87a58d2eb2538583368df5add9dd66d79
Tx public key: eea17332f7e509a39a52c2d0aa1c80555931f9eee403a0030b69aceec4724073
Timestamp: 1705225531 Timestamp [UCT]: 2024-01-14 09:45:31 Age [y:d:h:m:s]: 01:079:13:59:24
Block: 935062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317955 RingCT/type: yes/0
Extra: 01eea17332f7e509a39a52c2d0aa1c80555931f9eee403a0030b69aceec47240730211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2354b99d0b49ab483e5b6477f7df656de8c01665d8b7532c2cff7e7651813d1 0.600000000000 1393078 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": 935072, "vin": [ { "gen": { "height": 935062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2354b99d0b49ab483e5b6477f7df656de8c01665d8b7532c2cff7e7651813d1" } } ], "extra": [ 1, 238, 161, 115, 50, 247, 229, 9, 163, 154, 82, 194, 208, 170, 28, 128, 85, 89, 49, 249, 238, 228, 3, 160, 3, 11, 105, 172, 238, 196, 114, 64, 115, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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