Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f37fa4da60a35e4e670307299494c375fccdc37edf6b24ebe44fbaae9b3b0df

Tx prefix hash: e0a6bae6a10a70424d45e6d61355626e60fb36e1d0af392a8f0e0560d2d950c8
Tx public key: 902705f10602753d03909e9484aecdcb3dcd906656eaef022715ec9e38f63671
Timestamp: 1712603737 Timestamp [UCT]: 2024-04-08 19:15:37 Age [y:d:h:m:s]: 01:211:06:35:16
Block: 996204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409677 RingCT/type: yes/0
Extra: 01902705f10602753d03909e9484aecdcb3dcd906656eaef022715ec9e38f6367102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2693c3479b132d369fbca4dbfca853ecb8c762e72872f37302f04f17c2761eeb 0.600000000000 1456620 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": 996214, "vin": [ { "gen": { "height": 996204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2693c3479b132d369fbca4dbfca853ecb8c762e72872f37302f04f17c2761eeb" } } ], "extra": [ 1, 144, 39, 5, 241, 6, 2, 117, 61, 3, 144, 158, 148, 132, 174, 205, 203, 61, 205, 144, 102, 86, 234, 239, 2, 39, 21, 236, 158, 56, 246, 54, 113, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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