Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c425cf250adf92027576aaee850f6678cc0faccf6e45fd7d6cdf025c402556ee

Tx prefix hash: ba8e613fa8ba638bb61e7736a527559c192833d9fd1b900e32ded5f198d4ba11
Tx public key: b547fdf55025310af684c83d1b42419a88b21f6d49b07fe7b26afb79fe514e8e
Timestamp: 1727858808 Timestamp [UCT]: 2024-10-02 08:46:48 Age [y:d:h:m:s]: 00:112:02:56:25
Block: 1122713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80112 RingCT/type: yes/0
Extra: 01b547fdf55025310af684c83d1b42419a88b21f6d49b07fe7b26afb79fe514e8e02110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 727c3ff0451b45fcf0c8ee7b3ad4dfd3f49313215ff6ba4eb57feccb6cef31d3 0.600000000000 1605214 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": 1122723, "vin": [ { "gen": { "height": 1122713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "727c3ff0451b45fcf0c8ee7b3ad4dfd3f49313215ff6ba4eb57feccb6cef31d3" } } ], "extra": [ 1, 181, 71, 253, 245, 80, 37, 49, 10, 246, 132, 200, 61, 27, 66, 65, 154, 136, 178, 31, 109, 73, 176, 127, 231, 178, 106, 251, 121, 254, 81, 78, 142, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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