Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e48144f8713fa4d779635e576fe2dc40750aeda496c9bea9fcc29b016d4acbe

Tx prefix hash: 1cde1463cf0f638d8ee5f12b11186de75e1e1927f8e8d96cad63b11586b5f11f
Tx public key: 74e0094fa3a0e82a4d4686418be7a23c5083b14c7da577a7f8d973f988b88799
Timestamp: 1722913707 Timestamp [UCT]: 2024-08-06 03:08:27 Age [y:d:h:m:s]: 00:247:17:54:02
Block: 1081706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176958 RingCT/type: yes/0
Extra: 0174e0094fa3a0e82a4d4686418be7a23c5083b14c7da577a7f8d973f988b88799021100000005e914dd15000000000000000000

1 output(s) for total of 0.600080000000 dcy

stealth address amount amount idx
00: 6e4f1ed8bf175368b3785974943c1bfea6ae57b7d051ba4ebb9b5cb6f81001a5 0.600080000000 1555525 of 0

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": 1081716, "vin": [ { "gen": { "height": 1081706 } } ], "vout": [ { "amount": 600080000, "target": { "key": "6e4f1ed8bf175368b3785974943c1bfea6ae57b7d051ba4ebb9b5cb6f81001a5" } } ], "extra": [ 1, 116, 224, 9, 79, 163, 160, 232, 42, 77, 70, 134, 65, 139, 231, 162, 60, 80, 131, 177, 76, 125, 165, 119, 167, 248, 217, 115, 249, 136, 184, 135, 153, 2, 17, 0, 0, 0, 5, 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