Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f60fae473cb949ca8f17046e356cb7d731dd783bc82a8434674b5e44b85749a0

Tx prefix hash: 174edb1237ce6c1ddb1c01a2a84adb31aafef697aae02e5fa4f1ad29b2797069
Tx public key: f0e7a644aac6e4eeb9608116e99d7315725c9ce8294fe1bbdd9bd613fb707a31
Timestamp: 1737874124 Timestamp [UCT]: 2025-01-26 06:48:44 Age [y:d:h:m:s]: 00:047:16:40:03
Block: 1205540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33907 RingCT/type: yes/0
Extra: 01f0e7a644aac6e4eeb9608116e99d7315725c9ce8294fe1bbdd9bd613fb707a31021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7248cac418fb3d384cf916431e92013c0d92ae2042f12d6789b7d5a2ae811a37 0.600000000000 1692237 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": 1205550, "vin": [ { "gen": { "height": 1205540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7248cac418fb3d384cf916431e92013c0d92ae2042f12d6789b7d5a2ae811a37" } } ], "extra": [ 1, 240, 231, 166, 68, 170, 198, 228, 238, 185, 96, 129, 22, 233, 157, 115, 21, 114, 92, 156, 232, 41, 79, 225, 187, 221, 155, 214, 19, 251, 112, 122, 49, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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