Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e4fb404d244b9ca9d4e9816ffaf18f2d48bdc53c048911040335e401da24218

Tx prefix hash: 97154d5f6703880b9d4ef562da9fd2ba4fa6cc5e20081de5446216c4542e4d83
Tx public key: 832070ddeb126aa9a40eece7d7849f38013b8ee5f58d9c48b729f08f1153ad43
Timestamp: 1706840821 Timestamp [UCT]: 2024-02-02 02:27:01 Age [y:d:h:m:s]: 01:360:13:21:46
Block: 948452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516398 RingCT/type: yes/0
Extra: 01832070ddeb126aa9a40eece7d7849f38013b8ee5f58d9c48b729f08f1153ad4302110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21daf6d4784388ca6d3591fb907ef724dc438886bfc35aa85f7169dfc4129d7c 0.600000000000 1406864 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": 948462, "vin": [ { "gen": { "height": 948452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21daf6d4784388ca6d3591fb907ef724dc438886bfc35aa85f7169dfc4129d7c" } } ], "extra": [ 1, 131, 32, 112, 221, 235, 18, 106, 169, 164, 14, 236, 231, 215, 132, 159, 56, 1, 59, 142, 229, 245, 141, 156, 72, 183, 41, 240, 143, 17, 83, 173, 67, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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