Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33f4ac892cffaadd2892dc7d0eb8a4da9c7bf26f82201a0c957637229f164c3d

Tx prefix hash: 497bcd15db3c3036200563f5bf0752cb79808cbae946e9f79102323683df7f71
Tx public key: 425ce9d7b8821e18a67df4269bf4eda8cd8a0d7e6633eaa205dd740b56d503d1
Timestamp: 1709822485 Timestamp [UCT]: 2024-03-07 14:41:25 Age [y:d:h:m:s]: 01:027:09:29:37
Block: 973189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280574 RingCT/type: yes/0
Extra: 01425ce9d7b8821e18a67df4269bf4eda8cd8a0d7e6633eaa205dd740b56d503d10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 125470c80e85f6afda483f368b14cbaa45546caa7c4402b0dda622c6304f1655 0.600000000000 1433122 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": 973199, "vin": [ { "gen": { "height": 973189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "125470c80e85f6afda483f368b14cbaa45546caa7c4402b0dda622c6304f1655" } } ], "extra": [ 1, 66, 92, 233, 215, 184, 130, 30, 24, 166, 125, 244, 38, 155, 244, 237, 168, 205, 138, 13, 126, 102, 51, 234, 162, 5, 221, 116, 11, 86, 213, 3, 209, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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