Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5616aed637d39de6e1a7bf461de9d767a6e0ffc756ad284b34401c45c14cbfde

Tx prefix hash: fea3b08f5f100ddb0809a033c8235003204bb9f87f6515485627d017cf16e6f3
Tx public key: 1c365c8dcfb1a8c44935d6324db1c851187b442791fd3b2244bc313852e46a7c
Timestamp: 1701063678 Timestamp [UCT]: 2023-11-27 05:41:18 Age [y:d:h:m:s]: 01:054:06:48:07
Block: 900561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300150 RingCT/type: yes/0
Extra: 011c365c8dcfb1a8c44935d6324db1c851187b442791fd3b2244bc313852e46a7c02110000000a33af99f4000000000000000000

1 output(s) for total of 0.636894574000 dcy

stealth address amount amount idx
00: 75f2132506d15063c3e2dd8bcf69eb2813a10cf19b6bc379f5aeb0813f44c83f 0.636894574000 1357068 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": 900571, "vin": [ { "gen": { "height": 900561 } } ], "vout": [ { "amount": 636894574, "target": { "key": "75f2132506d15063c3e2dd8bcf69eb2813a10cf19b6bc379f5aeb0813f44c83f" } } ], "extra": [ 1, 28, 54, 92, 141, 207, 177, 168, 196, 73, 53, 214, 50, 77, 177, 200, 81, 24, 123, 68, 39, 145, 253, 59, 34, 68, 188, 49, 56, 82, 228, 106, 124, 2, 17, 0, 0, 0, 10, 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