Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68066c03ffed5e253340ea493bcae5fc4b408f63b9af14dc57c1cac68a7b9e1f

Tx prefix hash: cd4f194f3e3fff5247741fa3698b29fba36dadf270fa9673f6e905b04e794850
Tx public key: 0f40cbaf7380f8f06ee274fa70e368b5b98101ba7f22660e2d2bbcb8e3893e2d
Timestamp: 1700188439 Timestamp [UCT]: 2023-11-17 02:33:59 Age [y:d:h:m:s]: 01:359:19:04:44
Block: 893300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516051 RingCT/type: yes/0
Extra: 010f40cbaf7380f8f06ee274fa70e368b5b98101ba7f22660e2d2bbcb8e3893e2d021100000002faf35c9c000000000000000000

1 output(s) for total of 0.673172346000 dcy

stealth address amount amount idx
00: 4c3e163d1bdfd5d53c391d2a07635bc69deb37bc2075e8a8b8a5321e0b16af8b 0.673172346000 1349463 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": 893310, "vin": [ { "gen": { "height": 893300 } } ], "vout": [ { "amount": 673172346, "target": { "key": "4c3e163d1bdfd5d53c391d2a07635bc69deb37bc2075e8a8b8a5321e0b16af8b" } } ], "extra": [ 1, 15, 64, 203, 175, 115, 128, 248, 240, 110, 226, 116, 250, 112, 227, 104, 181, 185, 129, 1, 186, 127, 34, 102, 14, 45, 43, 188, 184, 227, 137, 62, 45, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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