Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 826ca28a90ac73b0e2d580aea3bd020f123b6b0368f29ba1aed8843fe3f1ab80

Tx prefix hash: 9601f293340c25e29300bad2d20de149d9f1182fd711c5697733596ede1f44e0
Tx public key: b3cf8c509527a630fd926373a1cfeee8277c10e8f43a92c00bc6ed75f15b28a8
Timestamp: 1701464309 Timestamp [UCT]: 2023-12-01 20:58:29 Age [y:d:h:m:s]: 01:048:00:25:29
Block: 903879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295702 RingCT/type: yes/0
Extra: 01b3cf8c509527a630fd926373a1cfeee8277c10e8f43a92c00bc6ed75f15b28a8021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.620974309000 dcy

stealth address amount amount idx
00: 25c4ef2f9b616139bda00e65c2c7a8d443a5a07c5d6849fcf7d382b00b9d991f 0.620974309000 1360576 of 0

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": 903889, "vin": [ { "gen": { "height": 903879 } } ], "vout": [ { "amount": 620974309, "target": { "key": "25c4ef2f9b616139bda00e65c2c7a8d443a5a07c5d6849fcf7d382b00b9d991f" } } ], "extra": [ 1, 179, 207, 140, 80, 149, 39, 166, 48, 253, 146, 99, 115, 161, 207, 238, 232, 39, 124, 16, 232, 244, 58, 146, 192, 11, 198, 237, 117, 241, 91, 40, 168, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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