Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b6a68d58e49820340b5d3dbdc9577e36c532ce78213f023b5d4193062d7c3d9

Tx prefix hash: 4fe4bb98116e0da2a781bf0069318a9cde8741e934177dbd9c70be1446283272
Tx public key: 87259c2e07c38b1d1bc2bcc67131cec2a0cc02f212c387e9b9d19ca3cf82af56
Timestamp: 1699682344 Timestamp [UCT]: 2023-11-11 05:59:04 Age [y:d:h:m:s]: 01:072:04:53:00
Block: 889114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312972 RingCT/type: yes/0
Extra: 0187259c2e07c38b1d1bc2bcc67131cec2a0cc02f212c387e9b9d19ca3cf82af5602110000000475e3f0e9000000000000000000

1 output(s) for total of 0.695018282000 dcy

stealth address amount amount idx
00: 91056aa71b6f499da08188470dc46b1427777d842d851aa4905f69e2cd6aa8d6 0.695018282000 1345091 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": 889124, "vin": [ { "gen": { "height": 889114 } } ], "vout": [ { "amount": 695018282, "target": { "key": "91056aa71b6f499da08188470dc46b1427777d842d851aa4905f69e2cd6aa8d6" } } ], "extra": [ 1, 135, 37, 156, 46, 7, 195, 139, 29, 27, 194, 188, 198, 113, 49, 206, 194, 160, 204, 2, 242, 18, 195, 135, 233, 185, 209, 156, 163, 207, 130, 175, 86, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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