Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6379d6c3ce71eefa1d5d6b4ef958ba0a82d50a6bc59b1115b91fb70143f06e74

Tx prefix hash: 12c5651602abbc68ccd1b925377712839423292b40db26ec966733137f4a273e
Tx public key: 4a948a49e3cc221bc5f1293d9dff11a1f273dddce8a4ac3a50ff9bdf39d04606
Timestamp: 1713345670 Timestamp [UCT]: 2024-04-17 09:21:10 Age [y:d:h:m:s]: 00:357:01:25:08
Block: 1002381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255272 RingCT/type: yes/0
Extra: 014a948a49e3cc221bc5f1293d9dff11a1f273dddce8a4ac3a50ff9bdf39d0460602110000001159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bafc3643820995d22b17385d36c0409d2d78a034ab8706a70fad7863b061079 0.600000000000 1462897 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": 1002391, "vin": [ { "gen": { "height": 1002381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bafc3643820995d22b17385d36c0409d2d78a034ab8706a70fad7863b061079" } } ], "extra": [ 1, 74, 148, 138, 73, 227, 204, 34, 27, 197, 241, 41, 61, 157, 255, 17, 161, 242, 115, 221, 220, 232, 164, 172, 58, 80, 255, 155, 223, 57, 208, 70, 6, 2, 17, 0, 0, 0, 17, 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