Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb12f0a0a24d8e5084c092dcbfc33d3bbaee302ac0ed325949746b78c266e26

Tx prefix hash: ddd77ad8972fd65db334e3bf133f0e2c426233e47b5439f7eaa743b1088a0cf0
Tx public key: d76a14c25da1cc56ead1464717b665ae8d6f726ba21ae2c068ce1960f5d8059e
Timestamp: 1727571742 Timestamp [UCT]: 2024-09-29 01:02:22 Age [y:d:h:m:s]: 00:258:09:08:32
Block: 1120332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184444 RingCT/type: yes/0
Extra: 01d76a14c25da1cc56ead1464717b665ae8d6f726ba21ae2c068ce1960f5d8059e021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af956965dfbb341cb75b8964725fb8141a8a54680e5a288a5a12973d28f230a0 0.600000000000 1602209 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": 1120342, "vin": [ { "gen": { "height": 1120332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af956965dfbb341cb75b8964725fb8141a8a54680e5a288a5a12973d28f230a0" } } ], "extra": [ 1, 215, 106, 20, 194, 93, 161, 204, 86, 234, 209, 70, 71, 23, 182, 101, 174, 141, 111, 114, 107, 162, 26, 226, 192, 104, 206, 25, 96, 245, 216, 5, 158, 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