Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87491c79a6fcf3c1e141950d1920a6e8c1281de61d9777ede4db646c6b3e46a5

Tx prefix hash: a538938a4f6f14314ea766bf78a50070a5a0814b0c4eadbba558677c0ce707b3
Tx public key: f70f207faf43f6c65cd727b7ac0c54929975a6b8dbb3f8d3c421053662144262
Timestamp: 1722135937 Timestamp [UCT]: 2024-07-28 03:05:37 Age [y:d:h:m:s]: 00:234:19:09:23
Block: 1075263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167733 RingCT/type: yes/0
Extra: 01f70f207faf43f6c65cd727b7ac0c54929975a6b8dbb3f8d3c42105366214426202110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24f2fc9e9edf9c74f2902febfe5237c104b16ab93ced36aa54f82d4971eb8ec2 0.600000000000 1547788 of 15

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": 1075273, "vin": [ { "gen": { "height": 1075263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24f2fc9e9edf9c74f2902febfe5237c104b16ab93ced36aa54f82d4971eb8ec2" } } ], "extra": [ 1, 247, 15, 32, 127, 175, 67, 246, 198, 92, 215, 39, 183, 172, 12, 84, 146, 153, 117, 166, 184, 219, 179, 248, 211, 196, 33, 5, 54, 98, 20, 66, 98, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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