Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc858db5ce43a1e5b1bae02a7e75301b6bd433312635ff87f992eb20d4ff9dea

Tx prefix hash: aef867edd918faf6eb7e13e8916ab2133d07acb6a9ad03497d8d62927e548a4d
Tx public key: 7d429f41cf1b4c53171901264a138c3f6aa433fa555efe56872c8eac7b1e77ee
Timestamp: 1580268803 Timestamp [UCT]: 2020-01-29 03:33:23 Age [y:d:h:m:s]: 05:340:02:32:19
Block: 54815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1392019 RingCT/type: yes/0
Extra: 017d429f41cf1b4c53171901264a138c3f6aa433fa555efe56872c8eac7b1e77ee0211000000012264afe6000000000000000000

1 output(s) for total of 403.994986970000 dcy

stealth address amount amount idx
00: 45f6561a35f71ab79e7b2d2b64aabde9aa1e8809de91ad03dc0824e074f37cc2 403.994986970000 101309 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": 54825, "vin": [ { "gen": { "height": 54815 } } ], "vout": [ { "amount": 403994986970, "target": { "key": "45f6561a35f71ab79e7b2d2b64aabde9aa1e8809de91ad03dc0824e074f37cc2" } } ], "extra": [ 1, 125, 66, 159, 65, 207, 27, 76, 83, 23, 25, 1, 38, 74, 19, 140, 63, 106, 164, 51, 250, 85, 94, 254, 86, 135, 44, 142, 172, 123, 30, 119, 238, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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