Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b069bcaa9f3f73e438ca7a511efa7700df6c16c47f2184702fef99f66cd9786

Tx prefix hash: 9fe5f6d6b1b62c094c20f163e8150f5e36bf10c0c2188f0ff62fc5267769f0e5
Tx public key: dc954e39a149c4aa289923110009ca2e23089ec703e8c83069f623624036acd3
Timestamp: 1712993489 Timestamp [UCT]: 2024-04-13 07:31:29 Age [y:d:h:m:s]: 00:318:13:55:12
Block: 999451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227757 RingCT/type: yes/0
Extra: 01dc954e39a149c4aa289923110009ca2e23089ec703e8c83069f623624036acd302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a26abd1ccd744a9b65116f4e490dc7a971fb101d277aca7db43b73152554f34 0.600000000000 1459931 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": 999461, "vin": [ { "gen": { "height": 999451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a26abd1ccd744a9b65116f4e490dc7a971fb101d277aca7db43b73152554f34" } } ], "extra": [ 1, 220, 149, 78, 57, 161, 73, 196, 170, 40, 153, 35, 17, 0, 9, 202, 46, 35, 8, 158, 199, 3, 232, 200, 48, 105, 246, 35, 98, 64, 54, 172, 211, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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