Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a8d0b179eee0088fce47d600e23f22fcb55297804678a6c094edca86b090585

Tx prefix hash: c7552a1c83d8e64f3fbd67769508f8561446394c885bd10d04416e1344fbe376
Tx public key: 0022b3d7997dc4802c9fd18ff68c508b78623ccdf88b2f6642673db4d1724a6e
Timestamp: 1724851005 Timestamp [UCT]: 2024-08-28 13:16:45 Age [y:d:h:m:s]: 00:055:18:14:37
Block: 1097768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39912 RingCT/type: yes/0
Extra: 010022b3d7997dc4802c9fd18ff68c508b78623ccdf88b2f6642673db4d1724a6e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 262f14c3fb99c7dc24df31051d27a12883762ae7ed395afe42984ea10e2f1644 0.600000000000 1573251 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": 1097778, "vin": [ { "gen": { "height": 1097768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "262f14c3fb99c7dc24df31051d27a12883762ae7ed395afe42984ea10e2f1644" } } ], "extra": [ 1, 0, 34, 179, 215, 153, 125, 196, 128, 44, 159, 209, 143, 246, 140, 80, 139, 120, 98, 60, 205, 248, 139, 47, 102, 66, 103, 61, 180, 209, 114, 74, 110, 2, 17, 0, 0, 0, 2, 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