Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d70e151104d0b83d60ce41251252348b1d2630ce010ec5556ffb78c87c2b0280

Tx prefix hash: 7e0a123fd0a383856b121e252186edfbae0d2e0c9cf7b5de8717e0f598c6185d
Tx public key: 2017ce30d34f6fc23a7cb52f2250941d02accef7c84abf5df3f6f6c20d64c511
Timestamp: 1670172806 Timestamp [UCT]: 2022-12-04 16:53:26 Age [y:d:h:m:s]: 02:042:22:32:48
Block: 645370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552590 RingCT/type: yes/0
Extra: 012017ce30d34f6fc23a7cb52f2250941d02accef7c84abf5df3f6f6c20d64c51102110000000133af99f4000000000000000000

1 output(s) for total of 4.462942356000 dcy

stealth address amount amount idx
00: 0ff630949e9d78c0cf4dea17965947cd857678f1c096e95e61c334574f2abaf3 4.462942356000 1085531 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": 645380, "vin": [ { "gen": { "height": 645370 } } ], "vout": [ { "amount": 4462942356, "target": { "key": "0ff630949e9d78c0cf4dea17965947cd857678f1c096e95e61c334574f2abaf3" } } ], "extra": [ 1, 32, 23, 206, 48, 211, 79, 111, 194, 58, 124, 181, 47, 34, 80, 148, 29, 2, 172, 206, 247, 200, 74, 191, 93, 243, 246, 246, 194, 13, 100, 197, 17, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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