Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02766681d8117a5f7b42a1b8ddfd3a6eded61e8f4e67ba0b6e84949ae00e2f38

Tx prefix hash: ed9eb41dfc408d1ac0fdcb8cf873966ce45ad84e7dafa8cb79fa45591ba445d7
Tx public key: 74ce3505304f28af74aee57d2cae74db8b5f944686aa853c6b0940fe3fe5486a
Timestamp: 1734933172 Timestamp [UCT]: 2024-12-23 05:52:52 Age [y:d:h:m:s]: 00:173:04:43:22
Block: 1181266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123517 RingCT/type: yes/0
Extra: 0174ce3505304f28af74aee57d2cae74db8b5f944686aa853c6b0940fe3fe5486a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f92adc11a4a9ca80e3b99734cf5374f1794f249ccb4f4436de6dc800e9110443 0.600000000000 1667683 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": 1181276, "vin": [ { "gen": { "height": 1181266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f92adc11a4a9ca80e3b99734cf5374f1794f249ccb4f4436de6dc800e9110443" } } ], "extra": [ 1, 116, 206, 53, 5, 48, 79, 40, 175, 116, 174, 229, 125, 44, 174, 116, 219, 139, 95, 148, 70, 134, 170, 133, 60, 107, 9, 64, 254, 63, 229, 72, 106, 2, 17, 0, 0, 0, 5, 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