Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b5fafeac87d52d3610537a2ad283663c888dc37d613783c180d3d3e51a6cdf7

Tx prefix hash: 23fcad8bbd58a022cc99c7576ff6481a793f33ffef00f1d5ec189e19c00a6600
Tx public key: eb31be0671d8ab88ffbb911c685c69073d74ed8c823ee5a4e196c8d01f654629
Timestamp: 1711526192 Timestamp [UCT]: 2024-03-27 07:56:32 Age [y:d:h:m:s]: 01:222:21:29:33
Block: 987328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417948 RingCT/type: yes/0
Extra: 01eb31be0671d8ab88ffbb911c685c69073d74ed8c823ee5a4e196c8d01f65462902110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3baeaa3f1209eacf66318086ece9e3d4540a7bba5f263c6b57108475c229fce0 0.600000000000 1447569 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": 987338, "vin": [ { "gen": { "height": 987328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3baeaa3f1209eacf66318086ece9e3d4540a7bba5f263c6b57108475c229fce0" } } ], "extra": [ 1, 235, 49, 190, 6, 113, 216, 171, 136, 255, 187, 145, 28, 104, 92, 105, 7, 61, 116, 237, 140, 130, 62, 229, 164, 225, 150, 200, 208, 31, 101, 70, 41, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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