Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a928bb4f9c98ebadb7609c4790b06dbb3540486e9f7bdad4b95f5859e3630a3

Tx prefix hash: 0ac790c6067daf1c56a2b472132f1f1e0033cde5359b4ae905f81ab9ac4111d6
Tx public key: 79c47eb28019059db24a9c43346b070cb3ad57ef8a190c3a6bfd2c0961f0aebb
Timestamp: 1685152563 Timestamp [UCT]: 2023-05-27 01:56:03 Age [y:d:h:m:s]: 01:320:17:09:26
Block: 768901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490431 RingCT/type: yes/0
Extra: 0179c47eb28019059db24a9c43346b070cb3ad57ef8a190c3a6bfd2c0961f0aebb02110000000233af99f4000000000000000000

1 output(s) for total of 1.739049631000 dcy

stealth address amount amount idx
00: a5707295480a0934f56d863e6e9e34585a299e0c63cdabd5e9792a4b431ff13e 1.739049631000 1218124 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": 768911, "vin": [ { "gen": { "height": 768901 } } ], "vout": [ { "amount": 1739049631, "target": { "key": "a5707295480a0934f56d863e6e9e34585a299e0c63cdabd5e9792a4b431ff13e" } } ], "extra": [ 1, 121, 196, 126, 178, 128, 25, 5, 157, 178, 74, 156, 67, 52, 107, 7, 12, 179, 173, 87, 239, 138, 25, 12, 58, 107, 253, 44, 9, 97, 240, 174, 187, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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