Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57ca9f2e657feaa1a54ae3f808e5bee7956c9e6609ba4a663f3d9db2fd004e83

Tx prefix hash: 9681878be919314bd3ee254a0a0789e0fc9a8c021e1edac1130fee1e2be9d47b
Tx public key: cf743f4beff817f0758a66afeef868980ab6387d573ec67dd36d4722b7cbbed0
Timestamp: 1610223302 Timestamp [UCT]: 2021-01-09 20:15:02 Age [y:d:h:m:s]: 03:300:15:26:03
Block: 176708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 970357 RingCT/type: yes/0
Extra: 01cf743f4beff817f0758a66afeef868980ab6387d573ec67dd36d4722b7cbbed00211000000154ea414e5000000000000000000

1 output(s) for total of 159.401974615000 dcy

stealth address amount amount idx
00: ad5f6ce6da86b68df6fc228331ccd36b91119e4140604286355a4c1669b06a99 159.401974615000 338778 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": 176718, "vin": [ { "gen": { "height": 176708 } } ], "vout": [ { "amount": 159401974615, "target": { "key": "ad5f6ce6da86b68df6fc228331ccd36b91119e4140604286355a4c1669b06a99" } } ], "extra": [ 1, 207, 116, 63, 75, 239, 248, 23, 240, 117, 138, 102, 175, 238, 248, 104, 152, 10, 182, 56, 125, 87, 62, 198, 125, 211, 109, 71, 34, 183, 203, 190, 208, 2, 17, 0, 0, 0, 21, 78, 164, 20, 229, 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