Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e79777b8ddb4d346982a4065bf930d9d2bb9577166a0dd3f9f4f62951717983

Tx prefix hash: 4dc6d7b641314ea2b98f1fc731cd7e0c675ede4cf829eb1e96091d4cf6f79814
Tx public key: 86090042c98ce5a11445774050405f3c66a093c19d1759faaa6bb59b0dbe9ebb
Timestamp: 1720508305 Timestamp [UCT]: 2024-07-09 06:58:25 Age [y:d:h:m:s]: 00:276:01:44:10
Block: 1061775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197246 RingCT/type: yes/0
Extra: 0186090042c98ce5a11445774050405f3c66a093c19d1759faaa6bb59b0dbe9ebb02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 301cc764f9bf8248ae1f2e6e628e2feaf01716ad6390a3d0ea45531a89d26f97 0.600000000000 1532270 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": 1061785, "vin": [ { "gen": { "height": 1061775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "301cc764f9bf8248ae1f2e6e628e2feaf01716ad6390a3d0ea45531a89d26f97" } } ], "extra": [ 1, 134, 9, 0, 66, 201, 140, 229, 161, 20, 69, 119, 64, 80, 64, 95, 60, 102, 160, 147, 193, 157, 23, 89, 250, 170, 107, 181, 155, 13, 190, 158, 187, 2, 17, 0, 0, 0, 4, 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