Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6db322cdcc89b75c174d76ee7db8cc6d3efb4aca8faca2045a6f33dd2217d94

Tx prefix hash: 08595b8a624af6fc3a6827ba68639fb968703702cb74b98b884b271022f3e49e
Tx public key: f5f0e5e1b89d780fa827b3b269181750a4d3e2d94c2591c0f7bee81f92c6ab40
Timestamp: 1656928926 Timestamp [UCT]: 2022-07-04 10:02:06 Age [y:d:h:m:s]: 02:139:12:58:23
Block: 536364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 621071 RingCT/type: yes/0
Extra: 01f5f0e5e1b89d780fa827b3b269181750a4d3e2d94c2591c0f7bee81f92c6ab4002110000000133af99f4000000000000000000

1 output(s) for total of 10.251881202000 dcy

stealth address amount amount idx
00: 2536eaa5af3b314da5d04421b57e6abd3ca2d53294b59c122d5a9aa4d7212f3e 10.251881202000 966113 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": 536374, "vin": [ { "gen": { "height": 536364 } } ], "vout": [ { "amount": 10251881202, "target": { "key": "2536eaa5af3b314da5d04421b57e6abd3ca2d53294b59c122d5a9aa4d7212f3e" } } ], "extra": [ 1, 245, 240, 229, 225, 184, 157, 120, 15, 168, 39, 179, 178, 105, 24, 23, 80, 164, 211, 226, 217, 76, 37, 145, 192, 247, 190, 232, 31, 146, 198, 171, 64, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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