Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40d51877b6bf260db3b7ec2204ab2faa9528f160959b7e3553d690b235ef58f7

Tx prefix hash: 08ae919e3996e6235af99e9d7846c3de7df6044aabc423e66ceb4a699cd8b167
Tx public key: 4448e5a74060d7b564b98f90f5322a0456faf21244a5f73cfee8b0286adbd336
Timestamp: 1583079156 Timestamp [UCT]: 2020-03-01 16:12:36 Age [y:d:h:m:s]: 05:085:19:23:45
Block: 74559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1216027 RingCT/type: yes/0
Extra: 014448e5a74060d7b564b98f90f5322a0456faf21244a5f73cfee8b0286adbd336021100000126026b59f3000000000000000000

1 output(s) for total of 347.500857023000 dcy

stealth address amount amount idx
00: b3678e38448067f636fde0ed02122d71e8f1aea72bd50deea05fd028daaa7936 347.500857023000 137965 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": 74569, "vin": [ { "gen": { "height": 74559 } } ], "vout": [ { "amount": 347500857023, "target": { "key": "b3678e38448067f636fde0ed02122d71e8f1aea72bd50deea05fd028daaa7936" } } ], "extra": [ 1, 68, 72, 229, 167, 64, 96, 215, 181, 100, 185, 143, 144, 245, 50, 42, 4, 86, 250, 242, 18, 68, 165, 247, 60, 254, 232, 176, 40, 106, 219, 211, 54, 2, 17, 0, 0, 1, 38, 2, 107, 89, 243, 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