Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89794fde8c0db1380129b0372b97414daea6f167c609dcc1d799bfdd0190c534

Tx prefix hash: 5fc392304ef716aa9df95f9220ad3251e564284ae10cf1ad1c27135533b0f0ae
Tx public key: a4fc183e8ced083c35e5ae34a7a241e20ee1cf7e426a3c7efa600fdc944d47e1
Timestamp: 1710377031 Timestamp [UCT]: 2024-03-14 00:43:51 Age [y:d:h:m:s]: 01:027:07:26:45
Block: 977794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280491 RingCT/type: yes/0
Extra: 01a4fc183e8ced083c35e5ae34a7a241e20ee1cf7e426a3c7efa600fdc944d47e102110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75b06f0b67185f45f9eab958591c4ce1c47b40ef4723c115128479b2545814ad 0.600000000000 1437801 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": 977804, "vin": [ { "gen": { "height": 977794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75b06f0b67185f45f9eab958591c4ce1c47b40ef4723c115128479b2545814ad" } } ], "extra": [ 1, 164, 252, 24, 62, 140, 237, 8, 60, 53, 229, 174, 52, 167, 162, 65, 226, 14, 225, 207, 126, 66, 106, 60, 126, 250, 96, 15, 220, 148, 77, 71, 225, 2, 17, 0, 0, 0, 8, 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