Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 656deb4858b09aea5ff5ea895dfdf8ab7aa7dd7e453f3bc38bcb88c1eabbe813

Tx prefix hash: a095e174fe5311170718f79b370d9710d1ca1103f12e935d1322fbd5757443d0
Tx public key: 42777065304bf81213cad246aa26beb98d18f7aa4fb03f30afb830d9b21d62ab
Timestamp: 1722063603 Timestamp [UCT]: 2024-07-27 07:00:03 Age [y:d:h:m:s]: 00:278:04:35:24
Block: 1074657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198745 RingCT/type: yes/0
Extra: 0142777065304bf81213cad246aa26beb98d18f7aa4fb03f30afb830d9b21d62ab021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 511a783acc2aeb4e09488591b9475f1aaabd95f6b2f1d746d896d51e7dafb19e 0.600000000000 1547174 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": 1074667, "vin": [ { "gen": { "height": 1074657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "511a783acc2aeb4e09488591b9475f1aaabd95f6b2f1d746d896d51e7dafb19e" } } ], "extra": [ 1, 66, 119, 112, 101, 48, 75, 248, 18, 19, 202, 210, 70, 170, 38, 190, 185, 141, 24, 247, 170, 79, 176, 63, 48, 175, 184, 48, 217, 178, 29, 98, 171, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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