Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2472f99bafae56f74169f49e3aefd3bdf49f58b7aee99d01470ea03f564818df

Tx prefix hash: cec6490e618e61b2e07cb3c7ec5245e57bc759d31756f0cfadba86d2ad3980ac
Tx public key: 5b4965b509cc0be2f8d2e71a4548159f1eb1d6074dcf80f6792ef0f6c8164b40
Timestamp: 1589363413 Timestamp [UCT]: 2020-05-13 09:50:13 Age [y:d:h:m:s]: 04:296:11:41:20
Block: 100455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131767 RingCT/type: yes/0
Extra: 015b4965b509cc0be2f8d2e71a4548159f1eb1d6074dcf80f6792ef0f6c8164b40021100000502a86a1a65000000000000000000

1 output(s) for total of 285.201394964000 dcy

stealth address amount amount idx
00: 8595e1e6fd22e7f37b36d900adc25100bdabaee098f32b5ae5edf2f0668ff0c6 285.201394964000 176991 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": 100465, "vin": [ { "gen": { "height": 100455 } } ], "vout": [ { "amount": 285201394964, "target": { "key": "8595e1e6fd22e7f37b36d900adc25100bdabaee098f32b5ae5edf2f0668ff0c6" } } ], "extra": [ 1, 91, 73, 101, 181, 9, 204, 11, 226, 248, 210, 231, 26, 69, 72, 21, 159, 30, 177, 214, 7, 77, 207, 128, 246, 121, 46, 240, 246, 200, 22, 75, 64, 2, 17, 0, 0, 5, 2, 168, 106, 26, 101, 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