Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ada62665db69296760fd3156d9db9d858c068886c5257b79d772817c7b2c24e

Tx prefix hash: 25783f87877b796ff175d6d7cc4ec48aa0c545a313b2176182a9439edd3fdcf1
Tx public key: 67ae5cf0b309d7c92bc7102faebd4ab404b90792350114aa1ed478f17e776d80
Timestamp: 1672694289 Timestamp [UCT]: 2023-01-02 21:18:09 Age [y:d:h:m:s]: 02:055:17:02:22
Block: 666237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 561469 RingCT/type: yes/0
Extra: 0167ae5cf0b309d7c92bc7102faebd4ab404b90792350114aa1ed478f17e776d80021100000005faf35c9c000000000000000000

1 output(s) for total of 3.806100167000 dcy

stealth address amount amount idx
00: b46d21b7decc7a89e57087e88351c8d8e391d38facb1c27c20e35a54d76e1c06 3.806100167000 1107340 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": 666247, "vin": [ { "gen": { "height": 666237 } } ], "vout": [ { "amount": 3806100167, "target": { "key": "b46d21b7decc7a89e57087e88351c8d8e391d38facb1c27c20e35a54d76e1c06" } } ], "extra": [ 1, 103, 174, 92, 240, 179, 9, 215, 201, 43, 199, 16, 47, 174, 189, 74, 180, 4, 185, 7, 146, 53, 1, 20, 170, 30, 212, 120, 241, 126, 119, 109, 128, 2, 17, 0, 0, 0, 5, 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