Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2c4476b61ec5ee9c38d320238d45614855dc4a64432bd3e6a000382005c57a4

Tx prefix hash: c619cd3cc8ea79fa50f46571a3b8922f363ad3566d8180dac81235c189f6dc76
Tx public key: b79c237c09304e30b9cb9c99063ad1e9b60c859e43f08cd02c953afa27a6ab80
Timestamp: 1730426069 Timestamp [UCT]: 2024-11-01 01:54:29 Age [y:d:h:m:s]: 01:008:19:42:11
Block: 1143916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264718 RingCT/type: yes/0
Extra: 01b79c237c09304e30b9cb9c99063ad1e9b60c859e43f08cd02c953afa27a6ab80021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a7c729d00a7f063e298d938b54b885a84f126a7ed36fb06617d8c2fc82efc80 0.600000000000 1627949 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": 1143926, "vin": [ { "gen": { "height": 1143916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a7c729d00a7f063e298d938b54b885a84f126a7ed36fb06617d8c2fc82efc80" } } ], "extra": [ 1, 183, 156, 35, 124, 9, 48, 78, 48, 185, 203, 156, 153, 6, 58, 209, 233, 182, 12, 133, 158, 67, 240, 140, 208, 44, 149, 58, 250, 39, 166, 171, 128, 2, 17, 0, 0, 0, 4, 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