Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1766ece0cea1083316c040917a8efb9ff41844f3ef9e387029c80f8bab0320a

Tx prefix hash: 2ac7b8ea4e8fe38de9daa5d0c197868c2c9f770fd4cc4cfebd2ffd31f7600518
Tx public key: c26f58ba3a6bf2147af1af36f6b3763ec788104118b1a965304bb813e3c048e8
Timestamp: 1722925264 Timestamp [UCT]: 2024-08-06 06:21:04 Age [y:d:h:m:s]: 00:169:13:37:13
Block: 1081795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121285 RingCT/type: yes/0
Extra: 01c26f58ba3a6bf2147af1af36f6b3763ec788104118b1a965304bb813e3c048e802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2cdbfcb4b2513845e4d06bdd28c4634fd717f29b137a4ad62a9e0c22b8b69e1 0.600000000000 1555618 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": 1081805, "vin": [ { "gen": { "height": 1081795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2cdbfcb4b2513845e4d06bdd28c4634fd717f29b137a4ad62a9e0c22b8b69e1" } } ], "extra": [ 1, 194, 111, 88, 186, 58, 107, 242, 20, 122, 241, 175, 54, 246, 179, 118, 62, 199, 136, 16, 65, 24, 177, 169, 101, 48, 75, 184, 19, 227, 192, 72, 232, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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