Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21565a2a6cce212b68143c888f38ef06f9441f8c306c341f62968fc5c08963fd

Tx prefix hash: 37ab77ae006d7e2abc8197b7aaabb905c8df899a90fd666b86c7b5001730575d
Tx public key: a04916ac72ee4cf5d687bab67e324576b2d83f9946a4c4b4702a0f4690778512
Timestamp: 1717571982 Timestamp [UCT]: 2024-06-05 07:19:42 Age [y:d:h:m:s]: 00:293:18:49:18
Block: 1037437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209929 RingCT/type: yes/0
Extra: 01a04916ac72ee4cf5d687bab67e324576b2d83f9946a4c4b4702a0f469077851202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d10c427af2f6fbfb09e5ee628d9553fea5ad1a930218c8d549c64b2f8c39ebc7 0.600000000000 1505968 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": 1037447, "vin": [ { "gen": { "height": 1037437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d10c427af2f6fbfb09e5ee628d9553fea5ad1a930218c8d549c64b2f8c39ebc7" } } ], "extra": [ 1, 160, 73, 22, 172, 114, 238, 76, 245, 214, 135, 186, 182, 126, 50, 69, 118, 178, 216, 63, 153, 70, 164, 196, 180, 112, 42, 15, 70, 144, 119, 133, 18, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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