Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6224bdf445c17aa0174d0058794e8d169cd3fad02e9009562af15dba1ac6341c

Tx prefix hash: 8023b69db443f1fe48d0106aff069dfa31b46b41560ad2730e5a2a3e01eb4065
Tx public key: 62b463d0ace5e7cd54d48a1ae072000d2da59c546e9ca3b3aee77d33a415d8d6
Timestamp: 1705111185 Timestamp [UCT]: 2024-01-13 01:59:45 Age [y:d:h:m:s]: 01:084:11:17:37
Block: 934099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321466 RingCT/type: yes/0
Extra: 0162b463d0ace5e7cd54d48a1ae072000d2da59c546e9ca3b3aee77d33a415d8d602110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b44c3bb15e373ecdc48e86357ca4b2d7f3254d361c626f2e11ad41e2b954f7bb 0.600000000000 1392085 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": 934109, "vin": [ { "gen": { "height": 934099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b44c3bb15e373ecdc48e86357ca4b2d7f3254d361c626f2e11ad41e2b954f7bb" } } ], "extra": [ 1, 98, 180, 99, 208, 172, 229, 231, 205, 84, 212, 138, 26, 224, 114, 0, 13, 45, 165, 156, 84, 110, 156, 163, 179, 174, 231, 125, 51, 164, 21, 216, 214, 2, 17, 0, 0, 0, 10, 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