Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf17798991f32e027c45e4fefa1586c40d1ba776d681fda6cf28b1f334429d3a

Tx prefix hash: 90b1b04acfe0ca0747ed950928f22e6622b4defda3acf35f071ec85c8f2e3430
Tx public key: 640b5cbe7e9668e873412a83dd17e844d899e9ad84157b086867d0bb1dce6b7a
Timestamp: 1579948894 Timestamp [UCT]: 2020-01-25 10:41:34 Age [y:d:h:m:s]: 04:338:15:23:36
Block: 52668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132024 RingCT/type: yes/0
Extra: 01640b5cbe7e9668e873412a83dd17e844d899e9ad84157b086867d0bb1dce6b7a02111726488400000000000000000000000000

1 output(s) for total of 410.680901795000 dcy

stealth address amount amount idx
00: e6a0b847895749abc04a2bd18aa68bf45aa1fd45ef6054b33b4691d91cf9dce1 410.680901795000 97597 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": 52678, "vin": [ { "gen": { "height": 52668 } } ], "vout": [ { "amount": 410680901795, "target": { "key": "e6a0b847895749abc04a2bd18aa68bf45aa1fd45ef6054b33b4691d91cf9dce1" } } ], "extra": [ 1, 100, 11, 92, 190, 126, 150, 104, 232, 115, 65, 42, 131, 221, 23, 232, 68, 216, 153, 233, 173, 132, 21, 123, 8, 104, 103, 208, 187, 29, 206, 107, 122, 2, 17, 23, 38, 72, 132, 0, 0, 0, 0, 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