Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 933ffff039776a06f8ab9536b9310393840dbd1c5da1763ccba36296e2c9a901

Tx prefix hash: aa3fba268ebf01c1d22b32afb746b695cce9c420201fb73163e905785bf16733
Tx public key: 2b70b17c0b1f75765e9b1e3d2e3fdc2bef7e7cd8153a69397401097b458cc306
Timestamp: 1705790344 Timestamp [UCT]: 2024-01-20 22:39:04 Age [y:d:h:m:s]: 01:070:07:10:24
Block: 939721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311340 RingCT/type: yes/0
Extra: 012b70b17c0b1f75765e9b1e3d2e3fdc2bef7e7cd8153a69397401097b458cc3060211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36bdb868da717cc133b780aceb2753eac20f00a26fac4433bc2b9a451023b623 0.600000000000 1397833 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": 939731, "vin": [ { "gen": { "height": 939721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36bdb868da717cc133b780aceb2753eac20f00a26fac4433bc2b9a451023b623" } } ], "extra": [ 1, 43, 112, 177, 124, 11, 31, 117, 118, 94, 155, 30, 61, 46, 63, 220, 43, 239, 126, 124, 216, 21, 58, 105, 57, 116, 1, 9, 123, 69, 140, 195, 6, 2, 17, 0, 0, 0, 3, 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