Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f266e14e9459ce37a8f1de106a55ba257afda1b8e5360833d36a343dbac92adc

Tx prefix hash: 77ee0e6a45762f7a4a1c1cc886f9edae38da5f76d4692899618a4ec622b7fb15
Tx public key: cafa40fa991f22cb8b10e3c3e3abfd528ab922f792a4112bcba956b17a1f2c78
Timestamp: 1588733534 Timestamp [UCT]: 2020-05-06 02:52:14 Age [y:d:h:m:s]: 04:234:04:40:39
Block: 98627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1084120 RingCT/type: yes/0
Extra: 01cafa40fa991f22cb8b10e3c3e3abfd528ab922f792a4112bcba956b17a1f2c7802110000006386362411000000000000000000

1 output(s) for total of 289.206847130000 dcy

stealth address amount amount idx
00: f7fa57f33a4168cc113bc84d0944766d2e07fb381871cdb92dc0f058c74dacbe 289.206847130000 174337 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": 98637, "vin": [ { "gen": { "height": 98627 } } ], "vout": [ { "amount": 289206847130, "target": { "key": "f7fa57f33a4168cc113bc84d0944766d2e07fb381871cdb92dc0f058c74dacbe" } } ], "extra": [ 1, 202, 250, 64, 250, 153, 31, 34, 203, 139, 16, 227, 195, 227, 171, 253, 82, 138, 185, 34, 247, 146, 164, 17, 43, 203, 169, 86, 177, 122, 31, 44, 120, 2, 17, 0, 0, 0, 99, 134, 54, 36, 17, 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