Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9570b4390027140844f8f1bc44ef9d4c9976218080ddf97876a732d51c90ebc6

Tx prefix hash: a07ca356e5dce14eeb5d6e784bbaf6b44fefcd6c8875bd08bbb0e9bc834b4cb1
Tx public key: c41d79b15cedee85e0f5309763a8277788d71d2d045e5463ffcddb3bf0ca65fd
Timestamp: 1577707227 Timestamp [UCT]: 2019-12-30 12:00:27 Age [y:d:h:m:s]: 05:311:01:43:17
Block: 34999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1369823 RingCT/type: yes/0
Extra: 01c41d79b15cedee85e0f5309763a8277788d71d2d045e5463ffcddb3bf0ca65fd0211000000028a2ee0d9000000000000000000

1 output(s) for total of 469.931588699000 dcy

stealth address amount amount idx
00: 133def3e2699ce6506bcd50eaa088914107ac762348a6a9c6bd4fe0f226526a7 469.931588699000 58966 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": 35009, "vin": [ { "gen": { "height": 34999 } } ], "vout": [ { "amount": 469931588699, "target": { "key": "133def3e2699ce6506bcd50eaa088914107ac762348a6a9c6bd4fe0f226526a7" } } ], "extra": [ 1, 196, 29, 121, 177, 92, 237, 238, 133, 224, 245, 48, 151, 99, 168, 39, 119, 136, 215, 29, 45, 4, 94, 84, 99, 255, 205, 219, 59, 240, 202, 101, 253, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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