Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe820b7d16235d9faa39fe9d8f99edee98b1c7ce002798af43b4b929e636e791

Tx prefix hash: 3b63acd62ac62d1de271a5876ddeed0bccf64a8cfd275158c8e11f4b998d6196
Tx public key: db5663b89055469e6c809cecfe33e6633e0a2e29c79b881f7a533f17b807e055
Timestamp: 1731224078 Timestamp [UCT]: 2024-11-10 07:34:38 Age [y:d:h:m:s]: 00:130:04:45:53
Block: 1150510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92902 RingCT/type: yes/0
Extra: 01db5663b89055469e6c809cecfe33e6633e0a2e29c79b881f7a533f17b807e0550211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a642fcdc105f0feb03f596d19689f6c72a3c0643e73acbf271d7520697e36a21 0.600000000000 1635849 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": 1150520, "vin": [ { "gen": { "height": 1150510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a642fcdc105f0feb03f596d19689f6c72a3c0643e73acbf271d7520697e36a21" } } ], "extra": [ 1, 219, 86, 99, 184, 144, 85, 70, 158, 108, 128, 156, 236, 254, 51, 230, 99, 62, 10, 46, 41, 199, 155, 136, 31, 122, 83, 63, 23, 184, 7, 224, 85, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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