Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dd4f43b8d29ba21630f1ba246c70e7f1e742a76cf7bcb0a148cdd28483128ee

Tx prefix hash: 30e82bd8041057c79fc4c2e26617adc5574eab119e25533e9d96f66c043712ab
Tx public key: 64e39f366039dc575d9bf2a628a75b074ead5b8147cf69f18895f8b47f42d696
Timestamp: 1716218699 Timestamp [UCT]: 2024-05-20 15:24:59 Age [y:d:h:m:s]: 01:170:09:37:20
Block: 1026214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380368 RingCT/type: yes/0
Extra: 0164e39f366039dc575d9bf2a628a75b074ead5b8147cf69f18895f8b47f42d69602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c37026b83cfa619fca2b9fc27c6831240227a3d5310ec230ddd317f8ce8ea3bf 0.600000000000 1493171 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": 1026224, "vin": [ { "gen": { "height": 1026214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c37026b83cfa619fca2b9fc27c6831240227a3d5310ec230ddd317f8ce8ea3bf" } } ], "extra": [ 1, 100, 227, 159, 54, 96, 57, 220, 87, 93, 155, 242, 166, 40, 167, 91, 7, 78, 173, 91, 129, 71, 207, 105, 241, 136, 149, 248, 180, 127, 66, 214, 150, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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